Project Overview

The Government of Alberta (GoA) has embarked on transforming the work of government to deliver simpler, more efficient, and better services for the citizens of Alberta, thereby ensuring that the needs of Albertans are effectively met in the digital age. The Province has a strategic role within government to drive efficiencies, innovation and modernization. The Digital Design and Delivery Division (DDD) is the Province’s new centre for digital delivery. It was established to maximize capability and confidence in modern digital practice by ensuring service quality and value through standards and controls. This includes utilizing human-centred design approaches together with agile methodology and modern data practices.

DDD works in partnership with GoA ministries to deliver programs that better serve Albertans.

DDD requires up to twenty-seven (27) QA Automation Developers to work with DDD on service innovation, program review and digital transformation projects across the GoA. The QA Automation Developer(s) will work as part of cross-functional program review or product delivery teams. These teams, led by GoA product owners and DDD work collaboratively, and collectively participate in a full range of activities including field research, backlog definition and refinement, and sprint planning and execution. Digital transformation projects review the current state of services, identify future opportunities, and then deliver new services that are efficient, effective and affordable.

QA Automation Developer(s) will be responsible for overseeing the quality in the delivery of digital services and ensuring that a team’s focus is on quality. A QA Automation Developer is typically responsible for creating test plans, test cases, and scenarios, identifying required test types, assets, and data environments and tools, and the creating automated test suites.

Scope of Services

The QA Automation Developer(s) will be required on a full-time basis, working across two (2) to three (3) projects. Time, location, and frequency of work will vary depending on the needs of the particular project. At the end of each term, it is expected that the QA Automation Developer(s) may work a maximum of 1,960 hours, unless otherwise agreed upon with the Province. However, QA Automation Developer(s) may be required to work fewer or more hours depending on the nature and needs of their work, as directed by the Province.

Services and project deliverables should evolve as the work progresses, in response to emerging user and business needs, as well as design and technical opportunities. However, the following must be delivered (iteratively) over the course of the project:

• Take the lead in ensuring the delivery of quality digital services:
• Create test plans to support frequent delivery of features with consistent and satisfactory quality;
• Create test cases and scenarios;
• Design and implement system tests;
• Design and implement load and performance tests; and
• Design and implement security tests.
• Manage automation that allows for rapid and frequent delivery:
• Implement automated test suites; and
• Coordinate contributions to automated test suites.
• Support and encourage the adoption of quality practices on a team such as code linting, test coverage, and Behavior/Test Driven Development (BDD/TDD).
• Support any initiatives regarding the use of re-usable testing components/suites, the creation of test databases or the use of AI during testing.
• Support a team in defining metrics for service quality:
• Contribute to and coordinate automated metrics collection; and
• Contribute to and coordinate automated generation of reports and Artifacts on quality.

The Province and the Contractor shall determine changes to Services and Materials as required. The Province and the Contractor will determine changes to Services and Materials through the Artifacts.

Location of Work

QA Automation Developer(s) will primarily work remotely; however, may be required to attend meetings or work sessions in Edmonton on reasonable notice from the Province. At the time of providing such notice, the Province will advise of the expected duration of any such meetings or work sessions. However, time to travel and any associated expenses to and from Edmonton will be at no cost to the Province.

The Province reserves the right to alter this work arrangement on reasonable notice to the QA Automation Developer(s). The Supplier and the QA Automation Developer(s) will be consulted about the alteration in work arrangement; however, the Province retains ultimate discretion as to the appropriate work arrangement.

Some travel within Alberta may be required to conduct field research and user interviews. The Province will make arrangements for travel for field research and user interview purposes where possible at no cost to the province.

Work must be done within Canada.

Facilities

QA Automation Developer(s) shall be responsible for providing all of their equipment, including computers, software, printers, supplies, desks and chairs. However, the Province shall ensure that the QA Automation Developer(s) have the necessary access and credentials to the GoA system.

In the event that the QA Automation Developer(s) are directed to work in-person, the Province shall provide the requisite office space, furniture and office supplies. However, the QA Automation Developer(s) shall continue to be responsible for providing computers and software and the Province shall continue to ensure that the QA Automation Developer(s) have the necessary access and credentials to the GoA system.

The virtual meeting tool for the Province is Microsoft Teams. Zoom may sometimes be used when needed, however, Zoom accounts are not provided by the Province.

Criminal Records Checks

Upon request by the Province, the QA Automation Developer(s) shall, at no cost to the Province, provide a current criminal record check. A QA Automation Developer may be rejected if, in the opinion of the Province, the criminal record is unacceptable.

Should a QA Automation Developer be assigned to a team working for Justice, prior to performing Services, the QA Automation Developer must provide the Province with an Enhanced Security Clearance. A QA Automation Developer may be rejected if, in the opinion of the Province, the Enhanced Security Clearance or equivalent is unacceptable. The Province does not receive any information specific to the reason an Enhanced Security Clearance may be rejected. Participating law enforcement agencies only identify if an applicant’s clearance is not accepted.

QA Automation Developer(s) should be aware that over the course of the WO, QA Automation Developer(s) may be required to complete higher-level security clearances, such as the Royal Canadian Mounted Police Top Secret Clearance. Please ensure applicants are eligible to apply if required by the ministry.

Acceptance by the Province of all QA Automation Developer(s) requires written approval from the Province following acceptable security clearances.

Evaluation

The evaluation criteria will be distributed within the following categories. Subject to the requirements of the Freedom of Information and Protection of Privacy Act (FOIP), the evaluation of Responses shall be confidential, and not released to any party.

1. Requirements - 40%
2. Interview - 50%
3. Pricing - 10%

Incumbency:

There are incumbents for up to 22 positions and up to 5 new positions requested. However, for this and all other opportunities, the Province seeks the best person to fill the role.

Anticipated Interview Dates:

Interviews are estimated to be held between August 18th - August 26th.

Mandatory Training Courses:

Once hired the resource will be required to complete all mandatory training which includes but is not limited to FOIP, Security/Cybersecurity, Information Management, and Respect in the Workplace. There may also be other mandatory and/or optional training.

SUBMISSION MUST INCLUDE:
ALL REQUIRED EXPERIENCE MUST BE DESCRIBED IN THE RESUME UNDER THE JOB/PROJECT WHERE EXPERIENCE WAS ATTAINED.

EACH JOB/PROJECT MUST CONTAIN THE TERM OF THE JOB/PROJECT IN THE FORMAT MMM/YYYY to MMM/YYYY.
THREE REFERENCES, FOR WHOM SIMILAR WORK HAS BEEN PERFORMED, MUST BE PROVIDED. THE MOST RECENT REFERENCE SHOULD BE LISTED FIRST. REFERENCE CHECKS MAY MOR MAY NOT BE COMPLETED TO ASSIST WITH SCORING THE PROPOSED RESOURCE.